These are the main goals:
In the end, the discussions ended in either flame wars or "do it this way ! - Won't work because !". So we just said: First we do something we know to handle. Then we have the experience to decide what is possible and how. And then we decide.
Also we want to be binary compatible to the old AmigaOS on Amiga. The reason for this is just that a new OS without any programs that run on it has no chance to survive. Therefore we try to make the shift from the old OS to our new one as painless as possible (but not to the extent that we can't improve AROS afterwards). As usual, everything has it's price and we try to decide carefully what that price might be and if we and everyone else will be willing to pay it.
See, there are plenty of people around who think that their feature is the most important and that "the AmigaOS has no future if this feature is not built in right now". We say: The AmigaOS' demise has nothing to do with missing features. The AmigaOS can do everything a modern OS should do. We see that there are possibilities to enhance the AmigaOS but if we do it, who would write the rest of the OS ? In the end, we would have lots of nice improvements to the original AmigaOS which would break most of the available software and worth nothing, because the OS itself would be missing. So we decided to block every attempt to implement major new features in the OS until it's more or less done.
If you want to use AROS' code in your project, you have to pay for this code if you earn money with the result. For PD developers, the code is still free.
Now there are of course limitations: You are not allowed to disassemble a software if the information you would gain by this process can be obtained by other means and it can be expected that one would use this is other means. And you must not tell others what you learned. A book like "Windows inside" is therefore illegal or at least dubious.
Since we avoid disassembling techniques (hey, we want the spirit and not the bugs) but use common available knowledge (including programming manuals) which don't fall below the NDA, this doesn't apply directly to AROS but what counts here is the intention of the law: It's ok to write a software which is compatible to some other software. Therefore we believe that AROS is protected by the law.
We are in loose contact with the author of UAE and there is a good chance that code for UAE will appear in AROS and vice versa. For example, UAE is interested in the source for the OS because it could run some apps much faster if it could replace the OS calls by native code. On the other hand, AROS needs hardware drivers (eg. audio.device).
Fact is that there is only few new software for the Amiga (although Aminet has never seen better times) and that hardware is also developed at a lower speed (but the most amazing gadgets appear right now). I say, the Amiga community (which is still there) just sit and wait. And if someone releases something which is a bit like the Amiga back in 1984, then that machine will boom again. And who knows, maybe you will get a CD along with the machine labeled "AROS" :-)
There will also be an archive with all tools we have installed to develop for AROS for the Amiga any time now (Linux and other Unixes find their developer packages pre-installed or at least much more easy to install from the Internet, eg. from www.suse.com (Germany) or www.redhat.com (USA)).
Several hundred Amiga experts (or at least what they thought of themselves) tried for three years to find a way to implement MP (memory protection) into the AmigaOS. They failed. You should take it as a fact that the normal AmigaOS will never have something like Unix or WindowsNT.
But all is not lost. There are plans to integrate MP into AROS which will allow to protect at least new programs which know about MP. Some efforts in this area look really promising and in the end: Is it really a problem if your machine crashes ? Let me explain, before you nail me to a tree :-) The problem is not that the machine crashes, the problems are: 1. If that happens, you have no good idea why it did, so you have to poke with a 100ft pole into a swamp with a thick fog. 2. You loose your work. Rebooting the machine is really no issue.
So what we try to establish is a system which will at least alert if something dubious is happening and which can tell you in great detail what was happening when the machine crashed and which will save your work and *then* crash. There will also be a means to check what has been saved so you can be sure that you don't continue with corrupted data.
The same with VMM, RT, SMP and RTG. We are currently planning how to implement them and we make sure that adding these features will be painless but they are no #1 priorities right now. A very basic RT has been added recently, though.
2.14 How about PPC or PPC cards ? *New*
We are regularily asked about AROS on PPC. The answer has always been the same: There is no one on the AROS team who own a PPC so we can't do anything about this. We have ordered a PPC card from phase5 and a PIOS ONE and when they become available, AROS will be ported. But no one can tell at this stage, when that will happen. So it's not that we don't want, it's just that we can't.2.15 What does Amiga International say about AROS ? *New*
Short: Nothing. Long: We tried to get in contact with AI twice by EMail but got nothing back. Aaron Digulla will attend at the IPISA in Milano in November and maybe Petro Tyschtschenko will be there as well so we can meet him personally.
If you have comments or suggestions, email me at digulla@aros.fh-konstanz.de. 13. Aug 1997